Drop writting application metadata in muxed files #3843
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is it?
[✔] Bug fix (user facing)
[✖] Feature (user facing)
[✖] Code base improvement (dev facing)
[✔] Meta improvement to the project (dev facing)
Description of the changes in your PR
By default an encoder/muxer writes a metadata called "writing and/or encoder application" for example
Lavf5 8.38.100
in FFMPEG, NewPipe does the same and this PR will remove it.The following format muxers are afected:
Also, fixes most of checkstyle's issues (excepts those large method lines)
Fixes the following issue(s)
resolves #3839
Testing apk
app-debug.zip
Final notes
In non-muxed files original google's metadata are present:
Mp4, In Handler Reference Atoms :
WebM, in WritingApp and MuxingApp elements:
Agreement
[✔] I carefully read the contribution guidelines and agree to them.